(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION ONLY. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NWLite 1.1 / Windows 3.1 Compatibility
DOCUMENT ID#: FYI.P.6122
DATE: 29Jan93
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: FYI.P.6077
SYMPTOM: NA
ISSUE/PROBLEM
NWLite 1.1 / Windows 3.1 Compatibility
Installing Windows 3.1 on a NetWare Lite Network:
If you are upgrading from a previous version of Windows to Windows 3.1, we recommend that you delete the previous version of Windows from your hard drive before you begin installation of 3.1. This is recommended because Windows 3.1 handles many of the settings in the initialization files (*.INI) differently than before, and will not always convert these parameters to the new format. There are also many drivers, including all printer drivers, that have been changed from release 3.0 to release 3.1. By deleting any previous version of Windows before you install release 3.1, you ensure that all drivers will be upgraded to the correct versions.
The first section of this document describes installing Windows 3.1 on NetWare Lite 1.1 in both Stand Alone and Shared Network Versions. The second section, entitled DR DOS 6.0 Configuration Items, discusses general suggestions for configuring DR DOS 6.0, NetWare Lite 1.1, and Windows 3.1 to have a peak performance between the three. The last section, Tips for Running Windows 3.1, describes general items regarding Windows 3.1 and NetWare Lite 1.1, regardless of what operating system you are using.
Installing Windows 3.1
Installing a Stand Alone Version of Windows 3.1
Follow the regular installation procedures to install Windows 3.1 as a stand alone version. To be able to access network resources, run the setup program and select "No Network Installed" as the network type.
For more information, refer to the Getting Started with Microsoft Windows booklet included with Windows 3.1.
Installing a Shared Version of Windows 3.1
The following is intended for users who want to install windows in shared mode. You will need to follow the steps to install on a NetWare Lite Server, and then for a NetWare Lite Client. Please refer to the Getting Started with Microsoft Windows booklet, pages 6-12, for information about installing Windows on networks in general.
Steps for Configuring a Server:
1. Decide which Server you want to install the shared copy of Windows on. Note: There must be approximately 16 MB of hard disk space available on the server to install a sharable copy of Windows 3.1.
2. Insert the Windows DISK #1 in the disk drive, and go to that drive (i.e. a: <enter>).
3. Type SETUP /A. When Windows asks for the network path to which it should install, enter C:\WINDOWS, or some other path to which you want to install Windows. (If this directory does not exist, Windows will create it for you).
As you follow the prompts, a sharable copy of Windows will be installed on the server. Note: This will not create an executable copy of Windows. It merely creates a location where clients can pull the executable programs from once they have been setup (see steps for clients, below).
After the shared copy of Windows has been installed, the following steps must be taken to properly configure the network software on the server.
4. Enter the NetWare Lite menu utility, by typing NET, and pressing ENTER. Then select "Supervise the network" and then "Network directories." Create a network directory by pressing the INSERT key. Select the server where the WINDOWS directory is located, type a name for the network directory, then enter the path to which you installed Windows, from step 3 above. Hit escape to exit and save the changes, and exit back to the Main Menu.
5. At the Main Menu in the NET utility select "Supervise the Network" and then select "Server Configuration." The CLIENT TASKS option defaults to 10 at the time of NetWare Lite installation. Set the CLIENT TASKS in the FUTURE column to 15 per machine connected to the network. (For example, if you had three 3 computers on the network, you would set the client tasks to 45).
6. When NetWare Lite is installed, the FILES=xx in the CONFIG.SYS file is set to be at least 30. This needs to be increased on the server by 20 per machine connected. You can change this by using a text editor (such as DR-DOS 6.0 EDITOR) to edit the config.sys file.
7. After you have performed these steps for the server, reboot the server for these changes to take effect.
Steps for Configuring a Client:
There are three ways to setup Windows from the shared copy installed on the server in the steps above. Please refer to page 7 in Getting Started with Microsoft Windows for a further explanation of the three methods.
Option A. Copy all Windows 3.1 files to the Client machine's hard drive.
Setting up Windows in this way will give each user the fastest performance of Windows. However, it will also greatly increase the amount of disk space used, and forces all clients to have their own hard disks.
Option B. Only copy custom configuration files to the Client machine's hard drive. All other files will be run from the shared copy installed on the server in the steps above.
Setting up Windows in this way will take up less disk space than option A above. However, it will run slower and client machines still must have their own hard disks.
Option C. No files will be stored on the Client machine's hard drive. Instead, the custom configuration files will be stored in a subdirectory on a network server and all other files will be run from the shared copy of Windows installed on the server in the steps above.
Setting up Windows in this way is the most conservative as far as disk space is concerned. It also gives the option of leaving the client machines as "diskless workstations", or machines without hard disks. But it is also the slowest way to run Windows, as everything must be pulled off of the network any time Windows is run.
The steps below are instructions to install Windows from the shared copy using Options A, B, and C above.
Option A. Copy all files to the Client machine's hard drive.
1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory which was created on the server in the Steps for Configuring a Server listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type:
Net Map I: WIN31 <return>
2. Change to the drive you mapped (I: in this example)
I: <return>
3. Type SETUP and press ENTER, and follow the prompts to install a copy of Windows to your local drive. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Refer to Windows documentation for questions regarding the installation.
4. When Windows prompts you, choose to "let you make the modifications later". You will then be prompted a path and file name in which to place a file with Windows-proposed changes to your autoexec.bat and config.sys files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows.
DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the subdirectory to which you are installing Windwos is in the PATH= statement in your autoexec.bat file.
MS DOS If you are running MS DOS, you will want to look at the Windows-proposed autoexec.bat and config.sys files, to see the changes that it wanted to make for you. The changes you will be looking for are the following:
In the AUTOEXEC.BAT file, Windows will insert a line to run the Smartdrive disk caching utility. However, there have been some problems running with Smartdrive. See the section on Third Party Disk Caches, towards the end of this document. It is suggested tht you run with either NetWare Lite NLCache, or DR-DOS PCKwik disk cache.
In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which include the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems, or are running with a different memory manager, you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the config.sys file, which is a fix to MS-DOS to handle hardware interrupts.
5. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, depending on which ports you have capture to network printers, instead of the normal LPT1 and LPT2 ports. See Network Printing and Windows 3.1 later in this document.
In the printer configuration, you will need to turn off "Fast Printing Direct to Port" off. Printing with this enabled bypasses any DOS calls, and would therefore not be able to print to network printers. To do this, choose Connect at the printer definition window. The Fast Printing Direct to Port will need to be turned off.
6. Continue following the prompts to finish the installation of Windows.
After you finish the installation of Windows, you will need to edit the System.ini file in the directory to which you installed Windows. See the Changes to System.ini towards the end of this document.
You will now run Windows from your local drive, not from I:. Verify that the subdirectory on your local drive that you selected in SETUP is included in your AUTOEXEC.BAT file in the PATH= statement, as you will need this to run Windows.
Option B. Custom configuration files are copied to the Client machine's hard drive. All other files will be run from the shared copy installed on the server in the steps above.
1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory which was created on the server in the Steps for Configuring a Server listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type:
Net Map I: WIN31 <return>
2. Create a subdirectory on the Client's hard drive in which to put the custom files (i.e.: MD C:\DAVE <return>).
3. Go to the network drive containing the Windows files (I: in this example)
I: <return>
4. Type SETUP /N then follow the Windows installation instructions. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the subdirectory which you created in step 2 (i.e.: C:\DAVE). Also, at the configuration screen, select the Network option "No Network Installed."
5. When Windows prompts you, choose to "let you make the modifications later". You will then be prompted a path and file name in which to place a file with Windows-proposed changes to your autoexec.bat and config.sys files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows.
DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the network directory where the shared version of Windows is installed, and the user subdirectory to which you installed the custom configuration files (I: and C:\DAVE in this example), are both in the PATH= statement in your autoexec.bat file.
MS DOS If you are running MS DOS, you will want to look at the Windows-proposed autoexec.bat and config.sys files, to see the changes that it wanted to make for you. The changes you will be looking for are the following:
In the AUTOEXEC.BAT file, Windows will insert a line to run the Smartdrive disk caching utility. However, there have been some problems running with Smartdrive. See the section on Third Party Disk Caches, towards the end of this document. It is suggested tht you run with either NetWare Lite NLCache, or DR-DOS PCKwik disk cache.
In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which include the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems, or are running with a different memory manager, you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the config.sys file, which is a fix to MS-DOS to handle hardware interrupts.
6. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, depending on which ports you have capture to network printers, instead of the normal LPT1 and LPT2 ports. See Network Printing and Windows 3.1 later in this document.
In the printer configuration, you will need to turn off "Fast Printing Direct to Port" off. Printing with this enabled bypasses any DOS calls, and would therefore not be able to print to network printers. To do this, choose Connect at the printer definition window. The Fast Printing Direct to Port will need to be turned off.
7. Continue following the prompts to finish installing Windows.
After you finish the installation of Windows, you will need to edit the System.ini file in the subdirectory to which you installed Windows custom configuration files (C:\DAVE in this example). See the Changes to System.ini towards the end of this document.
Once you reboot, load the network by typing STARTNET. Then, once you have performed your drive mappings and printer captures, you can type WIN to enter Windows.
Option C. No files will be stored on the Client machine's hard drive. Instead, the custom configuration files will be stored in a subdirectory on a network server and all other files will be run from the shared copy of Windows installed on the server in the steps above.
1. Load NetWare Lite by typing STARTNET. Map a drive to the network directory which was created on the server in the Steps for Configuring a Server listed above. For example, if the Network Directory you created in step 4 above was WIN31, you would type:
Net Map I: WIN31 <return>
2. Create a subdirectory on the Server's hard drive in which to put the custom files (i.e.: MD C:\STEVE <return>).
3. Create a network directory that looks at the user's subdirectory.
Enter the NetWare Lite menu utility, by typing NET, and pressing ENTER. Then select "Supervise the network" and then "Network directories." Create a network directory by pressing the INSERT key. Select the server on which you want to store your custom files, then enter the path of the subdirectory you created in step 3, such as C:\STEVE.
4. Map a drive to this network directory:
NET MAP G: STEVE <return>
5. Go to the network drive containing the Windows files (I: in this example).
I: <return>
6. Type SETUP /N then follow the Windows installation instructions. When prompted to either run an Express Setup or a Custom Setup, choose Custom. This allows you to preview the changes that are being made to the different files on your computer. Note: At the prompt for the path of the Windows files, enter the drive you have mapped to the custom files network directory from step 4 above (in this example it would be G:). Also, at the configuration screen, select the Network option "No Network Installed."
7. When Windows prompts you, choose to "let you make the modifications later". You will then be prompted a path and file name in which to place a file with Windows-proposed changes to your autoexec.bat and config.sys files. Depending on which version of DOS you are using, you will need to make certain changes after installing Windows.
DR DOS 6.0 None of these changes are necessary if you are running DR DOS. You will only need to verify, after installing Windows, that the network directory where the shared version of Windows is installed, and the network directory to which you installed the custom configuration files (I: and G:\ in this example), are both in the PATH= statement in your autoexec.bat file.
MS DOS If you are running MS DOS, you will want to look at the Windows-proposed autoexec.bat and config.sys files, to see the changes that it wanted to make for you. The changes you will be looking for are the following:
In the AUTOEXEC.BAT file, Windows will insert a line to run the Smartdrive disk caching utility. However, there have been some problems running with Smartdrive. See the section on Third Party Disk Caches, towards the end of this document. It is suggested tht you run with either NetWare Lite NLCache, or DR-DOS PCKwik disk cache.
In the CONFIG.SYS file, Windows will usually try to include its own memory manager, which include the HIMEM.SYS file, and the EMM386.EXE file. For MS-DOS this should be fine. However, if you experience memory problems, or are running with a different memory manager, you will want to leave these lines how they were before the Windows installation. You will also want to include a line STACKS=9,256 in the config.sys file, which is a fix to MS-DOS to handle hardware interrupts.
8. Follow the prompts to continue the installation of Windows. Note: When prompted to install printers, select and install any printers you have connected. Make sure they are specified as connected to port LPT1.DOS, or LPT2.DOS, depending on which ports you have capture to network printers, instead of the normal LPT1 and LPT2 ports. See Network Printing and Windows 3.1 later in this document.
In the printer configuration, you will need to turn off "Fast Printing Direct to Port" off. Printing with this enabled bypasses any DOS calls, and would therefore not be able to print to network printers. To do this, choose Connect at the printer definition window. The Fast Printing Direct to Port will need to be turned off.
9. Continue following the prompts to finish installing Windows.
After you finish the installation of Windows, you will need to edit the System.ini file in the network directory to which you installed Windows custom configuration files (G: in this example). See the Changes to System.ini towards the end of this document.
Once you reboot, load the network by typing STARTNET. Then, once you have performed your drive mappings and printer captures, type WIN to enter Windows.
DR DOS 6.0 Configuration Items:
The following items are for maximizing performance of Windows 3.1 on a NetWare Lite network running DR DOS 6.0.
1. In order to run with Windows 3.1 you must have the DR DOS 6.0 April 92 Update diskettes. Because Windows 3.1 was released after DR DOS 6.0, there were changes made to several DR DOS files to be fully compatible with Windows.
2. If you are using the Super PC-Kwik (SUPERPCK) disk caching utility that comes with DR DOS 6.0 there are certain things you can do to optimize the performance of Windows and NetWare Lite 1.1. First, you will need to have a line in your config.sys file which calls the Super PC-Kwik Windows driver, called PCKWIN.SYS. A sample command line for this would be DEVICE=C:\DRDOS\PCKWIN.SYS.
There are also a few command line switches that should be changed or added. They are the following:
/H- This option needs to be added for compatibility with NetWare Lite. It turns off the advanced reads and writes that can cause data corruption on some networks. There will still be read caching that is performed; not just the advanced reads and writes.
/L:xxx
/R:xxx Both of these options, if present on the command-line of SUPERPCK, should be removed. PC-Kwik defaults to use all available extended or expanded memory for the disk cache. Then it will, if a request is made by some application such as Windows, turn around and lend up to half of that memory back. That is controlled by these options.
However, it is easier to optimize the disk cache in conjunction with Windows if we can control the exact amount of the cache. For this reason we use the next option.
/S:xxx This option tells SUPERPCK how much memory to use for its cache, and you don't have to worry about how much is getting lent back. You just tell the cache exactly how much you DO want it to use.
If you do not include an amount (xxx), the /S: option will default to all available extended memory. The following are suggested amounts of memory to allocate to the cache via the /S: parameter based on the amount of ram you have in your machine.
Amount of RAM: Suggested cache size:
Less than 2 MB RAM do not use a cache
2 - 4 MB RAM 512k cache
4 - 6 MB RAM 1024k cache
above 6 MB RAM 2048k cache
The reason for the small cache sizes is the fact that Windows needs all of the memory that it can get to perform at its peak. By taking RAM away from Windows and allocating it to a cache, Windows may be forced to use a swap file on disk, where it could have run more from RAM had no cache, or a smaller cache, been allocated. So by having a small cache, you increase disk performance, and you also leave as much memory available to Windows as possible so that it will be running at an optimum speed.
3. If you have a network card in a 386 or 486 machine that uses a RAM, or shared memory, address you need to exclude that address in the memory manager command line. To do this, edit your config.sys file, and change the EMM386.SYS command. The format will be similar to the following:
where /E tells the memory manager (emm386.sys) not to allocate the range from nnnn to mmmm to any other programs. (It is in use by your network card; and you need to make sure that no other programs are loaded at the same memory addresses). nnnn and mmmm represent beginning and ending range addresses for the range to exclude. The following table shows the most common RAM addresses used by network cards, and the values for nnnn and mmmm based on those values.
Memory addr nnnn* 8k----mmmm*----16k
C0000 C000 C1FF C3FF
C8000 C800 C9FF CBFF
CC000 CC00 CDFF CFFF
D0000 D000 D1FF D3FF
D8000 D800 D9FF DBFF
* nnnn indicates starting memory address as found in NET.CFG file.
* mmmm indicates suggested ending address to be used.
NOTE: If you don't know whether your network card needs 8k or 16k for shared memory, you should use the larger, 16k value.
NOTE: If you don't know the memory address your network card uses, you can type the command TYPE C:\NWLITE\NET.CFG and look at the MEM value. (The net.cfg file tells your card driver how to initialize your network card).
If you aren't using EMM386.SYS in the config.sys file, add a line in the [386Enh] section of the SYSTEM.INI file in your windows directory which reads:
EMMExclude=nnnn-mmmm
where nnnn and mmmm are values from the tables above. Don't worry if their is already an EMMExclude line in your System.ini file. Multiple copies of this line are valid and will operate correctly.
NOTE: For more information on the EMM386.SYS exclude command-line option , please see pages 17 through 19 in the DRDOS 6.0 Customization and Optimization Tips manual.
4. If you are running on a superstored drive, be aware that swap files (whether permanent or temporary) cannot exist on a compressed partition of your hard drive. If your entire hard drive is compressed, or if there is not enough room on the uncompressed partition, you will either have to run without a swap file, or go through a few steps to re-setup your superstore partition.
Swap files are written to the disk in non-standard formats. This gives it the benefit of a fast access time. However, swap files may not be created on superstored partitions.
If you decide you want to have a swap file on your hard drive that is superstored, and don't have the space on the uncompressed partition, the following steps can help you set up your drive again for use with windows.
a. backup all data on the compressed partition of your hard drive. You will be removing the superstor partition, and for this reason all data on the hard drive will be erased. If you don't have a backup of your data, you will lose it all.
b. uncompress the drive by running the superstore utility (sstor) and chosing "remove" to remove the superstore partition.
NOTE: If the entire hard disk was superstored, you may need to reinstall DR DOS, as removing the superstore partition will remove any files on your hard disk, and will therefore remove your DR DOS files.
c. re-create the superstore partition by running superstore and chosing "create". When prompted, enter the amount of space to be left uncompressed. You will need to enter this amount in KiloBytes ("K"). 1024 KiloBytes is equal to 1 MegaByte. Remember that this portion of the disk needs to be large enough for your boot files and your permanent swap file. (a 5 MB swap file is a good size).
d. you can now restore your data from your backup copy to your newly compressed superstore partition.
There is one more thing to remember about superstored partitions. Windows, when it looks for the memory manager (emm386.sys) will be looking for it in the same path from which it was loaded. You will need to make sure that the emm386.sys driver is in the same subdirectory on both the compressed and non-compressed partitions of your hard drive. For example, if the emm386.sys file is in the DRDOS subdirectory on your non-compressed partition, make sure that there is a DRDOS subdirectory with the same file in it on your compressed partition.
TIPS FOR RUNNING WINDOWS 3.1:
Network Operations
You should run Startnet.bat before entering Windows. You should also map drives and capture ports before entering Windows.
Mapped Drives and Connections
Windows will display an error message if you try to access a drive on a server that has gone down. Any attempt to access that drive will fail. Under regular DOS, this error is trapped and the client saves enough information to automatically restore the connection to that network directory when the downed server returns to the network. Windows prevents regular DOS from trapping this error. To restore connections to your mapped drive, exit Windows and re-issue the NET MAP command when the server is back on the network.
Network printing and Windows 3.1
If you want to print from Windows to a network printer, you must setup the printer in Windows as a printer on port LPT1.DOS (which replaces LPT1.OS2 in Windows 3.0) or LPT2.DOS, depending on which port is captured. This is to let Windows know that it is to use the information that DOS provides it (such as a NET CAPTURE command you may have issued to print to the network printer) to print to LPT1, instead of trying to go to its own physical LPT port.
In the printer configuration, you will need to turn "Fast Printing Direct to Port" off. Printing with this enabled bypasses any DOS calls, and would therefore not be able to print to network printers. To do this, go into the Control Panel, in Printers, and highlight the printer. This option will show up after highlighting the printer and choosing Connect. It needs to be turned off.
You will also want to disable the Print Manager inside of Windows for the best printing performance. The reason for this is that using the print manager only makes the print job go through two print spoolers, as it passes once through the print manager, and then through the NetWare Lite spooler. This only takes more time and will slow down your printing.
NetWare Lite Messages
Messages sent to network users through NetWare Lite will not be received if the user to whom you are sending the message is in Windows.
Windows Modes
If you are experiencing a problem that only occurs when NetWare Lite is loaded and if the problem seems unsolvable, experiment with the other Windows mode to see if the problem is corrected. The Windows mode can be changed by using one of the following command line parameters:
Standard Mode: WIN /S
Enhanced Mode: WIN /3
(note that Windows 3.1 does not include an option to run in Real Mode, as did version 3.0).
Swap Files
Windows 3.1 has the ability to use swap files to enhance the performance of multiple tasks. By default, Windows will try to create a swap file on your hard disk at installation. DO NOT try to create a permanent swap file on a network drive, or create temporary swap files on any network drive other than a separate user subdirectory to which other users will not have access. It will corrupt any other swap file that may be in that subdirectory. Every user needs to have access to their own swap files. If you do not have a local hard disk on which to store a permanent swap file, it is recommended you use a temporary swap file in your user subdirectory on the network. This will avoid conflicts between two users' permanent or temporary swap files. (note: if you are running a shared version of windows on the server, you should MAP drives to the network directories, and not use the DOS SUBST command. This is unique to Windows 3.1. In all other applications, using the DOS SUBST, command on a server, in place of the NET MAP command is recommended).
Interrupts
VPICDA.386 is a patch written by Microsoft that fixes problems that arise when network cards are set to an interrupt of 2,3, or 9 and above, for use with Windows 3.0. Microsoft states that you no longer need this patch with Windows 3.1. If you encounter problems using these interrupts, check to see if you have a conflict with some other device using the same interrupt. Interrupt 2 being used by a machine with a VGA monitor is the most common conflict that people run into. (see fax document 212 for information on interrupt and i/o address conflicts).
Base I/O Addresses
I/O addresses below 300 should not be used for network cards on machines which also use Windows.
Changes to SYSTEM.INI
Make sure that the following lines are in the [386Enh] section of the Windows SYSTEM.INI file:
[386Enh]
UniqueDOSPSP = ON
PSPIncrement=5
TimerCriticalSection=10000
ReflectDOSInt2A=ON
OverlappedIO=OFF
If you do not have these options set, you will not be able to enter Windows if you have NetWare lite loaded. You will be given a message that they need to be added, and returned to the DOS prompt. The purpose of these changes is to enhance the compatibility between Windows and networks.
Changes to WIN.INI
There are several options you can set in the WIN.INI file for network control. NetWare Lite does not require using anything other than the default values for these options. Consult your Windows documentation for further information if you wish to change these options.
Third Party Disk Caches
There are some third party disk caches which do not work with NetWare Lite v1.1, or networks in general. If you have problems with Windows running slowly with your disk cache, you may want to shrink the size of memory allocated to the disk cache, as explained in the section DR DOS 6.0 Configuration Items, number 2, which discusses Super PCKwik.
If you are using a disk cache other than the NetWare Lite NLCache, you will need to disable the advanced reads and writes, sometimes called delayed or deferred writes. To do this you will need to refer to the documentation of your particular disk cache.
If you have problems with corrupted files, or lockups, you may want to remove your disk cache. There are some, especially those which perform advanced reads, and delayed writes, which have compatibility problems with NetWare Lite.
Third Party Memory Managers
If you have questions about your memory manager, you may want to check the section DR DOS 6.0 Configuration Items, numbers 3 and 4, which discuss EMM386.SYS, the memory manager that ships with DR DOS 6.0. Though the syntax of commands may be different, the items that you need to do are usually the same. You will need to refer to your documentation on your memory manager to decide the best format for those commands.
